feat: improve Application Insights logging and telemetry handling#753
Merged
Roopan-Microsoft merged 18 commits intodevfrom Mar 25, 2026
Merged
feat: improve Application Insights logging and telemetry handling#753Roopan-Microsoft merged 18 commits intodevfrom
Roopan-Microsoft merged 18 commits intodevfrom
Conversation
Contributor
There was a problem hiding this comment.
Pull request overview
This PR adds Azure Application Insights (via Azure Monitor OpenTelemetry) initialization to the backend entrypoint so the service can emit telemetry when an Application Insights connection string is provided.
Changes:
- Import
configure_azure_monitorand conditionally configure Azure Monitor at startup based onAPPLICATIONINSIGHTS_CONNECTION_STRING. - Add startup log lines indicating whether Application Insights was configured.
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
content-gen/src/backend/app.py
Outdated
Comment on lines
+41
to
+49
| # Check if the Application Insights Instrumentation Key is set in the environment variables | ||
| instrumentation_key = os.getenv("APPLICATIONINSIGHTS_CONNECTION_STRING") | ||
| if instrumentation_key: | ||
| # Configure Application Insights if the Instrumentation Key is found | ||
| configure_azure_monitor(connection_string=instrumentation_key) | ||
| logging.info("Application Insights configured with the provided Instrumentation Key") | ||
| else: | ||
| # Log a warning if the Instrumentation Key is not found | ||
| logging.warning("No Application Insights Instrumentation Key found. Skipping configuration") |
There was a problem hiding this comment.
The comments/log messages and variable name refer to an "Instrumentation Key", but the code is reading APPLICATIONINSIGHTS_CONNECTION_STRING and passes it as connection_string. Please rename instrumentation_key to something like appinsights_connection_string and update the comments/messages to consistently refer to a connection string (or change the env var if you truly intend to use an instrumentation key).
Suggested change
| # Check if the Application Insights Instrumentation Key is set in the environment variables | |
| instrumentation_key = os.getenv("APPLICATIONINSIGHTS_CONNECTION_STRING") | |
| if instrumentation_key: | |
| # Configure Application Insights if the Instrumentation Key is found | |
| configure_azure_monitor(connection_string=instrumentation_key) | |
| logging.info("Application Insights configured with the provided Instrumentation Key") | |
| else: | |
| # Log a warning if the Instrumentation Key is not found | |
| logging.warning("No Application Insights Instrumentation Key found. Skipping configuration") | |
| # Check if the Application Insights connection string is set in the environment variables | |
| appinsights_connection_string = os.getenv("APPLICATIONINSIGHTS_CONNECTION_STRING") | |
| if appinsights_connection_string: | |
| # Configure Application Insights if the connection string is found | |
| configure_azure_monitor(connection_string=appinsights_connection_string) | |
| logging.info("Application Insights configured with the provided connection string") | |
| else: | |
| # Log a warning if the connection string is not found | |
| logging.warning("No Application Insights connection string found. Skipping configuration") |
content-gen/src/backend/app.py
Outdated
Comment on lines
+46
to
+49
| logging.info("Application Insights configured with the provided Instrumentation Key") | ||
| else: | ||
| # Log a warning if the Instrumentation Key is not found | ||
| logging.warning("No Application Insights Instrumentation Key found. Skipping configuration") |
There was a problem hiding this comment.
This file defines a module logger (logger = logging.getLogger(__name__)), but these new lines log via the root logging module. Please use the module logger (logger.info / logger.warning) so log records have the correct logger name and can be filtered/structured consistently with the rest of the file.
Suggested change
| logging.info("Application Insights configured with the provided Instrumentation Key") | |
| else: | |
| # Log a warning if the Instrumentation Key is not found | |
| logging.warning("No Application Insights Instrumentation Key found. Skipping configuration") | |
| logger.info("Application Insights configured with the provided Instrumentation Key") | |
| else: | |
| # Log a warning if the Instrumentation Key is not found | |
| logger.warning("No Application Insights Instrumentation Key found. Skipping configuration") |
AjitPadhi-Microsoft
requested review from
Avijit-Microsoft,
Prajwal-Microsoft,
Roopan-Microsoft,
Vinay-Microsoft,
aniaroramsft,
malrose07,
nchandhi and
toherman-msft
as code owners
AjitPadhi-Microsoft
temporarily deployed
to
production
GitHub Actions
Inactive
AjitPadhi-Microsoft
temporarily deployed
to
production
GitHub Actions
Inactive
Contributor
There was a problem hiding this comment.
Pull request overview
Copilot reviewed 3 out of 3 changed files in this pull request and generated 2 comments.
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
AjitPadhi-Microsoft
temporarily deployed
to
production
GitHub Actions
Inactive
AjitPadhi-Microsoft
temporarily deployed
to
production
GitHub Actions
Inactive
AjitPadhi-Microsoft
temporarily deployed
to
production
GitHub Actions
Inactive
AjitPadhi-Microsoft
temporarily deployed
to
production
GitHub Actions
Inactive
AjitPadhi-Microsoft
temporarily deployed
to
production
GitHub Actions
Inactive
AjitPadhi-Microsoft
temporarily deployed
to
production
GitHub Actions
Inactive
AjitPadhi-Microsoft
changed the title
AjitPadhi-Microsoft
temporarily deployed
to
production
GitHub Actions
Inactive
AjitPadhi-Microsoft
temporarily deployed
to
production
GitHub Actions
Inactive
Roopan-Microsoft
approved these changes
Mar 25, 2026
Contributor
|
🎉 This PR is included in version 2.3.4 🎉 The release is available on GitHub release Your semantic-release bot 📦🚀 |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Purpose
Does this introduce a breaking change?
Golden Path Validation
Deployment Validation
What to Check
Verify that the following are valid
Other Information